/claim #54

This PR adds a focused, non-overlapping testing bootstrap slice for issue #54 in additional app/package workspaces beyond the current desktop/utils scope.

What's included

• add test scripts (pnpm exec vitest run) to:
  • apps/web-cluster
  • packages/web-api-contract
  • packages/web-domain
  • packages/sdk-recorder
• add one example test per workspace:
  • apps/web-cluster/src/cluster/container-metadata.test.ts
  • packages/web-api-contract/src/desktop.test.ts
  • packages/web-domain/src/utils.test.ts
  • packages/sdk-recorder/src/core/mime-types.test.ts

Validation

• pnpm --filter=@cap/web-cluster test
• pnpm --filter=@cap/web-api-contract test
• pnpm --filter=@cap/web-domain test
• pnpm --filter=@cap/sdk-recorder test

All four pass locally.

Notes

• Kept this PR intentionally scoped and mergeable; no lockfile churn and no unrelated dependency updates.
• The sdk-recorder example explicitly checks preferred codec priority order to provide a stronger baseline pattern for future tests.

AI-assisted with Codex; diff reviewed before submission.

Greptile Summary

This PR bootstraps Vitest test coverage in four previously-untested workspaces (apps/web-cluster, packages/sdk-recorder, packages/web-api-contract, packages/web-domain) by adding a test script and one representative test file per package.

• All four test files are logically sound: assertions match the source schemas and Effect service implementations, mock cleanup is handled correctly via afterEach, and the codec-priority test accurately reflects the PREFERRED_MIME_TYPES iteration order.
• All four package.json files add the test script but omit vitest from devDependencies, so pnpm exec vitest run will fail on a clean install or in CI where vitest is not hoisted from another workspace. No vitest.config.ts is provided for any of the new packages, diverging from the pattern established by every other workspace that already has tests.

Confidence Score: 3/5

The test logic is correct, but the missing vitest dependency will cause all four new test scripts to fail in CI or on a fresh clone.

The individual test files are well-written and faithfully cover their respective modules, but every package.json in the PR omits vitest from devDependencies. Running pnpm exec vitest run in an isolated package context resolves the binary from that package's own node_modules/.bin — and since vitest is never declared there, the command silently relies on hoisting from another workspace package. This is fragile enough to break turbo run test or any filtered run on a clean CI environment.

All four package.json files need vitest added to devDependencies before the test scripts are reliable.

Important Files Changed

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
apps/web-cluster/package.json:8
**`vitest` missing from devDependencies**

`pnpm exec vitest run` resolves the binary from the local `node_modules/.bin`. Since `vitest` is not declared as a `devDependency` here (or in any of the other three affected packages), the command will fail on a clean install or in CI. It likely passes locally only because vitest is hoisted from another workspace package (e.g. `apps/web`), which is an implicit, unreliable dependency. The same gap affects `packages/sdk-recorder`, `packages/web-api-contract`, and `packages/web-domain`.

### Issue 2 of 2
apps/web-cluster/package.json:8
**No `vitest.config` file for the new test suites**

None of the four new workspaces ship a `vitest.config.ts`, while every existing workspace that has a `test` script (`apps/desktop`, `apps/discord-bot`, `apps/web`) provides one. Without a config, Vitest uses default settings — no TypeScript path-alias resolution, no custom environment, and no `globals` injection. Adding at least a minimal config file per package aligns with the project's existing pattern.

_{Reviews (1): Last reviewed commit: "test: add package-level vitest examples ..." | Re-trigger Greptile}

Greptile also left 2 inline comments on this PR.